Content distribution system and method

ABSTRACT

A method and system for the secure distribution of content to authorized persons. A content provider uploads encrypted content to the system and specifies the institutions or individuals to which the content is to be provided and release conditions under which it is to be made available. Encrypted content is made available to a recipient together with a decryption code, if the identity of the recipient can be confirmed through a validation procedure and if the release conditions are met. The release conditions may include a time and date at which the release is to occur. The encrypted content has an associated sample which may be streamed to the recipient so as to permit the recipient to assess whether to download the fill encrypted content or not. In one embodiment, the validation procedure includes biometric validation of the identity of the recipient.

CROSS REFERENCE TO A RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 10/431,854, filed May 8,2003 and entitled CONTENT DISTRIBUTION SYSTEM AND METHOD, the subject matter of which is hereby incorporated by reference in its entirety.

FIELD OF THE INVENTION

This invention relates to the distribution of content to remote locations over a network, and more particularly to the secure distribution of content to authorized persons.

BACKGROUND OF THE INVENTION

The security and timing of the release of promotional material can be of vital importance to the developers of that material. For example, in the music industry a key component of marketing is the release of a single off a new album to radio stations. The listener response to a new single provides important information upon which wider marketing and release decisions will be based. For radio stations, the release of a new single also provides them with a promotional event to boost market share. Being the first station to premiere a new single by a popular artist can provide a competitive advantage.

Accordingly, controlling the timing of the release of a single and the persons receiving it is an important aspect of a recording label promotional program. Traditionally, the distribution is done by creating a promotion-only CD containing the single track and then distributing this CD to individual radio stations by courier. This method has many drawbacks, including the number of people who handle the CD while it is in transit. In many instances, a new single has been illicitly copied or stolen, distributed to unauthorized persons and released to the public prior to the intended release date and time. Moreover, this method is difficult to time accurately, is labor-intensive and subject to disruption from weather, labor strife, transportation problems and human error. Ensuring that competitive radio stations have access to a new single simultaneously and securely is important to the trust between the record label and the radio stations.

The same difficulties can be found in other industries and circumstances, including the distribution of new movies in the film industry and the distribution of new campaigns in the advertising industry. In general, the problem is experienced in any industry in which a content provider wishes to ensure the security and simultaneous timing of a distribution of content to a plurality of recipients.

As a further example, the advertising industry experiences difficulty in obtaining appropriate approvals from designated reviewers when a new proposed advertisement is developed. At present, it is common for advertising firms to create a dub of a proposed advertising spot and courier it to the intended reviewers, with the expectation that the reviewers will review the spot and telephone to grant their approval or disapproval. In some cases, it has been necessary to play a proposed advertisement to a reviewer over the telephone in order to obtain their approval or disapproval. Accordingly, there is presently an unacceptable level of delay, cost, uncertainty and inaccuracy involved in the distribution and approval of proposed new advertisements.

SUMMARY OF THE INVENTION

The present invention provides a method and system for the secure distribution of content to authorized persons. A content provider uploads encrypted content to the system and specifies the institutions or individuals to which the content is to be provided and release conditions under which it is to be made available. Decrypted content is made available to a recipient, if the identity of the recipient can be confirmed through a validation procedure and if the release conditions are met. The release conditions may include a time and date at which the release is to occur. In one embodiment, the validation procedure includes biometric validation of the identity of the recipient.

In one aspect, the present invention provides a method of distributing digital music to a plurality of recipients over a distributed computer network, each recipient having a recipient terminal connected to the network. The method includes registering the plurality of recipients by storing a user profile for each recipient in a distribution server. Each user profile includes user information uniquely identifying the associated recipient. Additional steps include receiving and storing, at the distribution server, a first music file delivered from a provider computer system connected to the network, and storing, at the distribution server, 1) a specific distribution list associated with the first music file and 2) at least one release condition, wherein the specific distribution list identifies one or more of the user profiles, and wherein the distribution server contains other music files, each music file having an associated distribution list and at least one associated release condition. A request for access is received from one of the recipient terminals that includes identity information. In response to that request, the identity information is matched with the user information stored in one of the user profiles to verify that the request for access is associated with a verified user profile, the distribution server is searched for distribution lists identifying the verified user profile, and information is provided to the recipient terminal regarding music files associated with distribution lists identifying the verified user profile. In response to the receipt, at the distribution sever, a request for the first music file from the recipient terminal, an evaluation is made as to whether the release condition is met, and, if the release condition is met, the recipient terminal is provided with a copy of the first music file.

In another aspect of the present invention, a system is provided for distributing digital music to a plurality of recipients over a distributed computer network, each recipient having a recipient terminal connected to the network. A music provider having a provider terminal is connected to the network. The system comprises a distribution server, including a processor, connected to the network for communicating with the provider terminal and the recipient terminals. The distribution server is configured to receive a request for access from one of the recipient terminals, the request for access including identity information. A computer-readable storage device is accessible to the distribution server and stores a user profile for each recipient, music files uploaded by one or more provider terminals, a distribution list for each of the music files, and at least one release condition associated with each music file. Each user profile includes user information identifying the associated recipient. Each distribution list identifies one or more of the user profiles based on selections received from the provider terminal when uploading the associated music file. The system additionally comprises an identity verification module executable by the processor to configure the distribution server to, in response to the request for access, match the identity information with the user information stored in one of the user profiles to verify that the request for access is associated with a verified user profile, search the distribution server for distribution lists identifying the verified user profile, and provide information to the recipient terminal identifying music files associated with distribution lists identifying the verified user profile. The distribution server is configured to receive a request for on of the first music files from said one of the recipient terminals, evaluate whether the release condition is met, and, if the release condition is met, provide the appropriate recipient terminal with a copy of the first music file.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made, by way of example, to the accompanying drawings which show an embodiment of the present invention, and in which:

FIG. 1 shows a block diagram of an embodiment of a content distribution system according to the present invention;

FIG. 2 shows a flowchart outlining an embodiment of the steps for loading content into a distribution system according to the present invention;

FIG. 3 shows a flowchart outlining an embodiment of the steps for distributing content to recipients according to the present invention; and

FIG. 4 shows, in flowchart form, an embodiment of a content approval process according to the present invention.

DESCRIPTION OF SPECIFIC EMBODIMENTS

Reference is first made to FIG. 1, which shows a block diagram of an embodiment of a content distribution system 10 according to the present invention. A plurality of recipient computer systems 12 and a remote distribution server 14 are mutually connected via a communications network 16, such as the Internet. Also connected to the communications network 16 is a content provider computer system 22. The content provider computer system 22 provides content to the server 14 for distribution to the recipient computer systems 12, as is further detailed below. In one embodiment, as described herein, the content is prerecorded digital music provided by a record label promotions director for distribution to radio stations, however it will be understood that the present invention is not limited to this embodiment. The content is not limited to music and may include other content, such as text, audio, video, computer software, or visual media like advertising and promotions. Other content will be understood by those skilled in the art upon a review of the following description of the present invention.

The content provider computer system 22 may be any conventional personal computer. The content provider computer system 22 is connected to a storage medium 24 containing the content intended for distribution to the recipient computer systems 12. The storage medium 24 may include ROM, RAM, floppy discs, compact discs, digital tape or any other medium on which content may be stored. The content provider computer system 22 includes a browser 26 for accessing web pages through the communications network 16. The content provider computer system 22 also includes an encryption module 28 for encoding, encrypting and uploading the content. It will be understood that the content provider computer system 22 may have more or fewer components than, or alternative components to, those shown in FIG. 1 and still provide the same functionality described herein.

Similarly, the recipient computer system 12 may be any conventional personal computer. The recipient computer system 12 also includes a browser 60 for accessing web pages through the communication network 16. The recipient computer system 12 includes a decryption module 62 for decrypting content obtained from the remote distribution server 14. The recipient computer system 12 is connected to a storage device 18 for storing any encrypted or decrypted content. In one embodiment, the storage device 18 is a mass storage device containing music in WAV format for use in radio broadcasts. Again, it will be understood that the recipient computer system 12 may have more or fewer components and still provide the same functionality described herein.

The remote distribution server 14 is configured to receive encrypted content from the content provider computer system 22 and to distribute the content to individual recipient computer systems 12, subject to verification of the identity of the user of the recipient computer system 12 and to the release time or date restrictions imposed by the user of the content provider computer system 22. The remote distribution server 14 ensures that decrypted content is not provided to unauthorized individuals or provided before the release time and date.

The remote distribution server 14 includes web pages 30 to provide a graphical user interface with the content provider computer system 22 and the recipient computer systems 12. The remote distribution server 14 also includes an identity verification module 32 and a business model management module 34. Connected to and accessible to the remote distribution server 14 is a mass storage device 20. The mass storage device 20 includes a rights profile database 38 and an asset database 36.

The identity verification module 32 permits access to the content distribution system 10 to be controlled based upon biometric verification of the identity of an individual using either a recipient computer system 12 or a content provider computer system 22. Verification of the individual's identity is accomplished by comparing the characteristics of the individual's typing cadence with a previously stored profile of the same activity collected during a registration process which involves reiterative entry of the same password or passphrase. An example of a keystroke dynamics biometric identity verification system can be seen in U.S. Pat. No. 4,805,222, which has been assigned to Net Nanny Inc. of Vancouver, B.C., Canada. In one embodiment of the present invention, the identify verification module 32 compares the individual's e-mail address, user name and password as well as biometric data, to prevent unauthorized access. By limiting distribution of content to particular individuals through validating the identity of the individuals, rather than the identity of a particular computer system, the possibility of unauthorized access to the content is minimized. In the context of a radio station, only one or two individuals at a particular radio station may be authorized to access content on the system 10.

The rights profile database 38 includes a database of individual user profiles for those users that have registered to access the system 10, either, as recipients or content providers. Each entry 50 in the rights profile database 38 may include identification information 52, such as user name, e-mail address or other identifying information. Each entry 50 may also include, in this embodiment, a radio station 52 with which the individual user is associated. Also included in each user entry 50 is biometric data 56 for use by the identity verification module 32 and one or more passwords 58. Further or other information may be included in the entries 50.

The asset database 36 includes the securely encrypted content provided by various content providers. Each entry 40 in the database includes song identification information 42 such as the artist's name, the title of the song and other information. Also included is a pointer or address information 44 for accessing the encrypted digital music single in the database. The entry 40 may also include a streaming unencrypted sample 46 of the music single. The sample allows a recipient to evaluate and pre-screen new upcoming singles and make programming decisions. The entry 40 also includes a release time and date 48 and a distribution list 49 of recipients that will be granted access to the digital music single. In one embodiment, the entry 40 includes an associated graphic (not shown), such as a photo, artist logo or album cover. The entry 40 may also include a pointer to an associated video (not shown) that may be downloaded with the digital music single or streamed to the recipient computer system 12. Further or other information may be included in the entries 40.

The business model management module 34 controls access to content of the asset database 36 based upon the distribution list 49 and the user profiles in the rights profile database 38, and it performs billing and reporting functions.

In operation, a content provider, such as a record label promotions director, uses the content provider computer system 22 to upload an encrypted digital music single to the remote distribution server 14. Reference is made to FIG. 2, which shows a flowchart 100 outlining an embodiment of the steps for loading content upon the server 14. To begin the process, the content provider uses the encryption module 28 to select content from the storage medium 24 (step 100-1). The storage medium 24 may be the artist's unreleased CD placed in the CD drive of the content provider computer system 22. The encryption module 28 is then employed to compress (step 100-2) and encrypt (100-3) the content. The content having been selected, compressed and encrypted, the encryption module 28 causes the browser 26 to be launched and to access the web pages 30 provided by the server 14 (step 100-4). The web pages 30 to which the encryption module 28 directs the browser 26 step the content provider through the process of uploading the encrypted digital file.

To upload a track, the content provider enters identification data 42 (step 100-5), such as the name of the track and the artist's name. Other information may be entered, such as the length of the track or the title of an associated album. The content provider then chooses a release time and date 48 (step 100-6). The content provider next selects a distribution list 49 of the individuals or radio stations that will be entitled to receive the single (step 100-7). The encrypted content is then uploaded to the server 14 for storage on the mass storage device 20 (step 100-8). If there are associated graphics or video for distribution with the encrypted digital music single, then those are also uploaded to the server 14. The server 14 assesses whether the transfer was successful (step 100-9) and sends an error message (step 100-10) to the content provider computer system 22 if the upload failed. If successful, the server 14 sends a confirmation to the content provider computer system 22 (step 100-11). The server 14 may also send a notification to the recipients in the distribution list 49 to alert them to existence of an upcoming single release.

FIG. 3 shows a flowchart 200 outlining an embodiment of the steps for distributing content to recipients. A radio station music director, for example, may access a new single release through the content distribution system 10 by using a recipient computer system 12. The music director may employ the browser 60 to access the web pages 30 on the server 14 (step 200-1). If the music director has a user profile in the rights profile database 38 then he or she may log on using their biometric password (step 200-2). The identity verification module 32 will verify their identity. If the music director does not have a valid user profile, then he or she will be directed through a registration process to establish a user profile (step 200-3).

Once the identity of the music director has been verified, the system 10 accesses the assets database 36 and the rights profile database 38 and determines which singles have a distribution list 49 that includes the music director or his radio station (step 200-4). The system 10 will then display information regarding the singles that the music director is entitled to access (step 200-5).

In one embodiment, the information will include singles prior to their release date. The music director may choose to listen to sample tracks (step 200-6), which are then streamed unencrypted to the recipient computer system, for example in MP3 format (step 200-7). These sample tracks are of insufficient length or quality to be used for radio play and, thus, pose little risk insofar as the security of the single is concerned. The system 10 may permit the music director to tag or select singles as “favorites” or “notables”, allowing a music director to sort through hundreds of samples and easily return to those which require further consideration or download. Such a feature may also permit the music director to save his or her preferences so as to preserve the list of tagged files.

The music director may choose to download (step 200-8) any full length singles to which he or she has authorized access provided the single release time/date has been reached. If the release conditions are not met (step 200-9), the music director will receive an error notification informing him or her of the date and time at which they may return to download the single. In another embodiment, the music director may be permitted to download encrypted singles prior to the release date, but will not be provided with the decryption code for decrypting the singles until the release date and time. Singles are downloaded (step 200-10) in encrypted compressed WAV format and are decrypted and decompressed on the recipient computer system 12 using the decryption module 62 and the decryption code provided by the server 14.

Reference is now made to FIG. 4, which shows, in flowchart form, an embodiment of a content approval process 300. In this embodiment, the content is a proposed advertisement prepared by an advertising firm. Using the system 10 (FIG. 1), the process 300 begin in step 300-1 when an individual at the firm, such as a traffic manager, employs the content provider computer system 22 (FIG. 1) to upload the content to the server 14 (FIG. 1), as described above. In addition to uploading the content, the advertising firm specifies one or more reviewers for inclusion in the distribution list 49 (FIG. 1). In step 300-2, the system 10 notifies the reviewers that they are required to review and approve or disapprove of an advertisement. Reviewers may include any number of people whose views are important in evaluating the potential of a new advertising campaign. For example, the reviewers may include members of the advertising firm including the client representative, an executive responsible, a producer or the traffic manager. The reviewers may also include individuals associated with the client, such as personnel within the client's marketing department, executives, or others. In one embodiment, the distribution list 49 is tiered, whereby the first tier of reviewers are internal advertising firm reviewers and the second tier of reviewers are external client reviewers. In this embodiment, the second tier of reviewers is not notified about the proposed advertisement and cannot access the advertisement until the first tier of reviewers have granted approval to the proposed advertisement.

When a reviewer logs onto the system 10 (step 300-3) using a recipient computer system 12 (FIG. 1), the system 10 verifies his or her identity using the identity verification module 32 (FIG. 1) and the reviewer's personal biometric profile 56 (FIG. 1). Once a reviewer has logged onto the system 10, he or she may download the advertisement so as to review it (step 300-4). The advertisement may be stored in an encrypted and encoded format, such that decryption and decoding information would also be transmitted to the reviewer provided their identity was verified by the system 10. The advertisement might also be streamed to the recipient computer system 12, instead of being downloaded in a file format.

Once the reviewer has had an opportunity to evaluate the proposed advertisement, he or she is required to register his or her approval or disapproval. The system 10 receives the reviewer's answer as to whether the advertisement is approved and stores it (step 300-5). The system 10 may also permit the reviewer to submit comments or suggestions with their approval or disapproval or to make their approval subject to specified changes.

In step 300-6 the system 10 evaluates whether it has received a sufficient number of approvals according to a set of business rules established by the advertising firm. The default rule may be that every reviewer must have registered his or her approval or disapproval, however other rules may be applied. For example, it may be sufficient if the advertisement has been approved by the executive and the client representative, even though the producer has not given his or her approval.

Once a sufficient number of reviews have been obtained, the system 10 notifies the advertising firm, the traffic manager or another designated individual of the results of the approval process 300 (step 300-7). In an alternative embodiment, the system 10 notifies the firm of every reviewer's response as soon as it is received, rather than accumulating a sufficient number of responses to rule upon the advertisement. The advertising firm then reviews and evaluates the responses received and any comments or suggestions made.

If the advertisement has been approved, in accordance with whatever criteria or business rules are being applied, i.e. unanimous approval, majority approval, etc., then the advertising firm (through its traffic manager or another individual) may again access the system 10 so as to create a distribution list 49 for distributing the campaign to whatever radio stations or other media outlets are supposed to receive it. This distribution may then be made in the manner described above with reference to FIG. 3.

The present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Certain adaptations and modifications of the invention will be obvious to those skilled in the art. Therefore, the above discussed embodiments are considered to be illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. 

1. A method of distributing digital music to a plurality of recipients over a distributed computer network, each recipient having a recipient terminal connected to the network, comprising: registering the plurality of recipients by storing a user profile for each recipient in a distribution server, wherein each user profile includes user information uniquely identifying the associated recipient; receiving and storing, at the distribution server, a first music file delivered from a provider computer system connected to the network; storing, at the distribution server, 1) a specific distribution list associated with the first music file and 2) at least one release condition, wherein the specific distribution list identifies one or more of the user profiles, and wherein the distribution server contains other music files, each music file having an associated distribution list and at least one associated release condition; receiving a request for access from one of the recipient terminals, the request for access including identity information; in response to the request, matching the identity information with the user information stored in one of the user profiles to verify the request for access is associated with a verified user profile, searching the distribution server for distribution lists identifying the verified user profile, and providing information to the recipient terminal regarding music files associated with distribution lists identifying the verified user profile, receiving, at the distribution sever, a request for the first music file from the recipient terminal; and in response to the receipt of the request, evaluating whether the release condition is met, and if the release condition is met, then providing the recipient terminal with a copy of the first music file.
 2. The method claimed in claim 1, wherein said user information comprises a username and password, and wherein the identity information in the request for access comprises a submitted username and submitted password, and wherein matching includes identifying the verified user profile based on the submitted username and confirming that the submitted password matches the password stored in the verified user profile.
 3. The method claimed in claim 1, wherein said identity information in the request for access comprises a unique code associated with the recipient terminal.
 4. The method claimed in claim 1, wherein said release condition includes a time and a date before which the recipient terminal cannot be provided with the copy of the first music file.
 5. The method claimed in claim 1, further including, before receiving the request for access, notifying said plurality of recipients identified in said specific distribution list of the availability of said first music file.
 6. The method claimed in claim 1, wherein said first music file comprises an encrypted music file, and wherein providing the recipient terminal with the copy includes downloading the encrypted music file to the recipient terminal and providing the recipient terminal with decryption code for decrypting the encrypted music file to produce said copy.
 7. The method claimed in claim 1, wherein said first music file comprises an encrypted music file, and wherein providing the recipient terminal with the copy includes decrypting said encrypted music file to produce said copy and downloading said copy to the recipient terminal.
 8. The method claimed in claim 7, wherein downloading includes streaming.
 9. The method claimed in claim 1, wherein the distribution list and release condition are received at the distribution server from the provider computer system.
 10. A method of distributing digital music to a plurality of recipients over a distributed computer network using a distribution server connected to the network, each recipient having a recipient terminal connected to the network, wherein the distribution server includes a user profile for each recipient, and wherein each user profile includes user information identifying the associated recipient, the method comprising: accessing the distribution server through a provider computer system connected to the network; selecting a first music file on the provider computer system; uploading the first music file from the provider computer system to the distribution server; and creating, 1) a specific distribution list associated with the first music file and 2) at least one release condition for the release of the first music file, wherein the specific distribution list identifies one or more of the user profiles, and wherein the distribution server contains other music files, each music file having an associated distribution list and at least one associated release condition, wherein, on receiving a request for access to the distribution server from one of the recipient terminals, the request for access including identity information, the distribution server is configured to match the identity information with the user information stored in one of the user profiles to verify the request for access is associated with a verified user profile, search the distribution server for distribution lists identifying the verified user profile, and provide information to the recipient terminal regarding music files associated with distribution lists identifying the verified user profile, and wherein on receiving a request for the first music file from the recipient terminal, the distribution server is configured to evaluate whether the release condition is met and, if the release condition is met, then to provide the recipient terminal with a copy of the first music file.
 11. The method claimed in claim 10, wherein said release condition includes a time and a date before which the recipient terminal cannot be provided with the copy of the first music file.
 12. The method claimed in claim 10, wherein the creating step is performed by a content provider using the provider computer system.
 13. A method of obtaining digital music over a distributed computer network, the distributed computer network having a distribution server storing a first music file, a specific distribution list associated with the first music file, and at least one release condition, wherein the specific distribution list identifies one or more user profiles stored on the distribution server, and wherein the distribution server contains other music files, each music file having an associated distribution list and at least one release condition, the method comprising: registering with a distribution server using a recipient terminal connected to the network, the registering step including providing user information identifying a recipient, wherein, in response to the registration, the user information is stored by the distribution server in a first user profile that includes the user information; sending a request for access to the distribution server from the recipient terminal, the request for access including identity information, wherein, in response to the request, the distribution server 1) matches the identity information with the user information stored in the first user profile to verify that the request for access is associated with a verified user profile, and 2) searches the distribution server for distribution lists identifying the verified user profile; receiving information at the recipient terminal from the distribution server regarding music files associated with distribution lists identifying the verified user profile; sending a request for the first music file to the distribution server from the recipient terminal, wherein, in response to receipt of the request for the first music file, the distribution server evaluates whether the release condition is met; and if the release condition is met, then receiving a copy of the first music file at the recipient terminal from the distribution server.
 14. The method claimed in claim 13, wherein said user information comprises a username and password, and wherein the identity information in the request for access comprises a submitted username and submitted password, and wherein the distribution server is configured to verify the request for access by identifying the first user profile based on the submitted username and confirming that the submitted password matches the password stored in the first user profile.
 15. The method claimed in claim 13, wherein said identity information in the request for access comprises a unique code associated with the recipient terminal.
 16. The method claimed in claim 13, wherein said release condition includes a time and a date before which the recipient terminal cannot receive the copy of the first music file.
 17. The method claimed in claim 13, further including, before sending the request for access, receiving email notification of the availability of said first music file from the distribution server.
 18. The method claimed in claim 13, wherein said first music file comprises an encrypted music file, and wherein receiving the copy includes receiving the encrypted music file at the recipient terminal, receiving decryption code from the distribution server, and decrypting the encrypted music file using said decryption code to produce said copy at the recipient terminal.
 19. The method claimed in claim 13, wherein said first music file comprises an encrypted music file, and wherein receiving the copy includes receiving a decrypted copy of said encrypted music file at the recipient terminal.
 20. The method claimed in claim 19, wherein receiving the decrypted copy includes receiving a stream containing the decrypted copy.
 21. A system for distributing digital music to a plurality of recipients over a distributed computer network, each recipient having a recipient terminal connected to the network, a music provider having a provider terminal connected to the network, the system comprising: a distribution server, including a processor, connected to the network for communicating with the provider terminal and the recipient terminals, wherein the distribution server is configured to receive a request for access from one of the recipient terminals, the request for access including identity information; a computer-readable storage device accessible to the distribution server and storing a user profile for each recipient, wherein each user profile includes user information identifying the associated recipient, music files including a first music file, uploaded by one or more provider terminals, a distribution list for each of the music files, including a first distribution list associated with the first music file, each distribution list identifying one or more of the user profiles based on selections received from the provider terminal when uploading the associated music file; at least one release condition associated with each music file; an identity verification module executable by the processor to configure the distribution server to, in response to the request for access, match the identity information with the user information stored in one of the user profiles to verify that the request for access is associated with a verified user profile, search the distribution server for distribution lists identifying the verified user profile, and provide information to the recipient terminal identifying music files associated with distribution lists identifying the verified user profile, wherein the distribution server is configured to receive a request for the first music file from said one of the recipient terminals, evaluate whether the release condition is met, and, if the release condition is met, provide said one of the recipient terminals with a copy of the first music file.
 22. The system claimed in claim 21, wherein said user information comprises a username and password, and wherein the identity information in the request for access comprises a submitted username and submitted password, and wherein the user verification module configures the distribution server to identify the verified user profile based on the submitted username and to confirm that the submitted password matches the password stored in the verified user profile.
 23. The system claimed in claim 21, wherein said identity information in the request for access comprises a unique code associated with the recipient terminal.
 24. The system claimed in claim 21, wherein said release condition includes a time and a date before which the recipient terminal cannot be provided with the copy of the first music file.
 25. The system claimed in claim 21, wherein the distribution server is configured to send a notification to the plurality of recipients identified in said first distribution list regarding the availability of said first music file.
 26. The system claimed in claim 21, wherein said first music file comprises an encrypted music file, and wherein the distribution server is configured to provide said one of the recipient terminals with a copy by downloading the encrypted music file to said one of the recipient terminals and providing said one of the recipient terminals with decryption code for decrypting the encrypted music file to produce said copy.
 27. The system claimed in claim 21, wherein said first music file comprises an encrypted music file, and wherein the distribution server is configured to provide said one of the recipient terminals with a copy by decrypting said encrypted music file to produce said copy and downloading said copy to said one of the recipient terminals.
 28. A method of distributing digital music to a plurality of recipients over a distributed computer network, each recipient having a recipient terminal connected to the network, comprising: registering the plurality of recipients by storing a user profile for each recipient in a distribution server, wherein each user profile includes user information identifying the associated recipient; receiving and storing, at the distribution server, a first music file delivered from a provider computer system connected to the network; receiving, from the provider computer system, and storing at the distribution server, 1) a specific distribution list associated with the first music file and 2) at least one release condition for release of the first music file, wherein the specific distribution list associates the first music file with one or more user profiles, and wherein the distribution server contains other music files, each music file having an associated distribution list; receiving, at the distribution server, a request for access from one of the recipient terminals, the request for access including identity information; at the distribution server, in response to the request, matching the identity information with the user information stored in one of the user profiles to verify the request for access is associated with a verified user profile, searching the distribution server for distribution lists containing associations with the verified user profile, and providing information to the recipient terminal regarding music files associated with the verified user profile, receiving, at the distribution server, a request for the first music file from the recipient terminal; evaluating whether the release condition is met; and if the release condition is met, then providing the recipient terminal with a copy of the first music file from the distribution server.
 29. A method of distributing digital music to a plurality of recipients over a distributed computer network, each recipient having a recipient terminal connected to the network, comprising: registering the plurality of recipients by storing a user profile for each recipient in a distribution server, wherein each user profile includes user information uniquely identifying the associated recipient; receiving, at the distribution server, a plurality of music files delivered from provider computer systems connected to the network; storing the music files in the distribution server; storing, in the distribution server, a distribution list for each music file and a release condition for each music file, wherein each distribution list identifies at least one of the user profiles; receiving a request for access from one of the recipient terminals, the request for access including identity information; in response to the request, matching the identity information with the user information stored in one of the user profiles to verify the request for access is associated with a verified user profile, and determining which music files have a distribution list that includes the verified user profile; receiving, at the distribution sever, a request from the recipient terminal to access one of the music files; and in response to the receipt of the request, determining whether the release condition is met, and if the release condition is met, then providing the recipient terminal with a copy of the first music file. 